-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
managing global configuration #24
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Errors are super informative.
Resolve the comments, then we can merge.
Still looking into why the lint test is failing. @parthvshah Any thoughts?
.gitignore
Outdated
@@ -42,7 +42,7 @@ node_modules/ | |||
jspm_packages/ | |||
|
|||
# Configuration file | |||
src/config.ts | |||
config/default.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the default.json exist by default?
The default flow should work without any modifications to the repo. And if the user wants to change the default mechanism, we will have to add in another json, and pass that to the config library (through env or any other mechanism)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, will update the PR
So I think this is the issue. Looks like the linter fails if you are trying to add a new file and it isn't present in the repo. This would explain the issue with PR #23 too. Still looking into this. |
Description of PR
Improve managing global configuration
Relevant Issues
Fixes #8
Checklist
Optional notes
In case the user has not created the config file, it throws an error saying:
If the file is present but is empty, in that case it throws the following error: